Anomaly Example: JavaScript Errors

In this example, a system administrator at ECommerce5000 receives an anomaly alert through YoBot about a spike in JavaScript errors:

Because this is a JavaScript error, no contributing factors information displays. Alternatively, the system administrator might also see the suddenly high rate of JavaScript errors on the Anomaly dashboard: 

To investigate the cause of the JavaScript errors anomaly, the system administrator opens the Anomaly dashboard. The JavaScript errors show a lot of instability over a sustained period of time, which points to an ongoing problem:

 

The system administrator then looks at the Top Page URLs list, which shows that the errors are happening on the site's homepage:  

They then look at the Top Resources list, which shows that the resource throwing the highest number of errors is a video:

The system administrator sends the information, including the video URL, to the developer team to further investigate and fix.